System and method for randomly generating and associating unlock codes and lock identifiers

ABSTRACT

The disclosure generally relates to a system and method for randomly generating unlock codes and identifiers for locks, and creating unlock code and identifier pairs. In an exemplary embodiment, the invention is integrated with, or part of, a distributed management system that controls access to various locations, such as, for example, self-storage units, hotel rooms, apartment buildings, storage containers, short-term housing rentals, lockers, equipment rooms, vaults, hospitals, airports, government facilities, nuclear power facilities, water treatment facilities, weapon storage facilities, aircraft cockpits, and any other setting that requires restricted, selective, or monitored access that can be remotely controlled, whereby users can request an unlock code via text messaging using a mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of, and claims benefit of andpriority to U.S. Non-Provisional patent application Ser. No. 17/547,289filed on Dec. 10, 2021, which claims priority to U.S. Non-Provisionalpatent application Ser. No. 17/151,609 filed on Jan. 18, 2021, whichclaims priority to U.S. Non-Provisional patent application Ser. No.16/545,247 filed on Aug. 20, 2019, which claims priority from U.S.Provisional Patent Application No. 62/722,379 filed Aug. 24, 2018, thecomplete subject matter of which is hereby incorporated herein byreference in its entirety, and further U.S. Non-Provisional patentapplication Ser. No. 16/545,247 is a continuation-in-part of, and claimsbenefit to, U.S. Non-Provisional patent application Ser. No. 15/962,583filed Apr. 25, 2018, which is a continuation-in-part of, and claimsbenefit to, U.S. Non-Provisional patent application Ser. No. 15/141,179filed Mar. 7, 2018, which claims benefit to U.S. Provisional PatentApplication No. 62/560,900 filed on Sep. 20, 2017, all of which areincorporated herein by reference in their entireties.

BACKGROUND Field of the Invention

The present invention relates generally to the field of over-lock andrelease systems for rentable facilities. More particularly, theinvention is a distributed management system for self-storage facilitiesthat allow for vacant units to be secured with over-locks, and whichallow the over-locks to be removed by customers without human or manualintervention from the self-storage facility.

Description of Related Art

Self-storage units are typically rented on a monthly basis. If acustomer is delinquent, and does not pay their rent to the self-storagefacility owner by an agreed-upon due date, the owner (i.e., landlord)has a right to prevent the customer from accessing the storage unit.Self-storage facility owners typically place an over-lock over thestorage unit door, such as through a hasp that prevents opening of thedoor. The over-lock is utilized until the customer pays the delinquentpast due balance on their account.

The process of placing, and removing over-locks, can be quite burdensomeon a self-storage facility owner, especially with large facilities withhundreds of storage units, the majority of which may be rented tomonth-to-month customers. After an over-lock is placed on a storageunit, the over-lock must ultimately be removed once the customer accountbecomes non-delinquent. Removing over-locks is time-consuming and costlybecause it requires personnel from the self-storage facility tophysically go to the storage unit and remove the over-lock.

In addition, the cost of conventional over-locks can be prohibitive.Many conventional over-locks are electronic and provide automated andremote locking/unlocking functions. Such over-locks oftentimes requiresignificant capital improvements on the storage structures, as theseover-locks must be installed behind the storage door on the interior ofthe space. Furthermore, these electronic locks inherently requireconstant power, and their continuous twenty-four hour operationincreases power consumption costs for the self-storage facility.

Furthermore, as with any complex electronic device, electronicover-locks are subject to failure and malfunction, and can requirecostly repairs to be conducted by an electrician, if not ultimatelyrequiring replacement.

Other conventional over-locks include standard combination locks.However, with a self-storage facility utilizing a limited number ofstandard combination over-locks, habitually delinquent customerseventually begin to recognize the unlock codes, and these over-locksbecome futile. The self-storage facility must then perpetually replaceover-locks with unlock codes that have become known and compromised.

Another disadvantage of standard combination over-locks is the potentialfor delayed access to the customer. If the customer makes a payment andbrings their account current when the self-storage management office isclosed or when personnel are unavailable, such as on weekends,after-hours, or holidays, the customer must then wait until the officeis open and there are personnel available to remove the over-lock. Thus,the customer cannot gain access to their storage unit and possessionsimmediately after making payment to bring their account current. Thedelay between such a payment and removal of the over-lock does not caterto tenants who may need immediate access to their storage unit.

Another challenge in managing self-storage facilities is securing vacantstorage units when they are not being rented. If the vacant units arenot properly secured, these units can be entered illegally and be usedto store items for free by unauthorized persons, could be used todiscard trash, and could be used for other illicit or illegal activitiesthat could pose liability and safety issues for the self-storagefacility and customers of the self-storage facility. Currently, vacantunits must be secured using traditional locks. In the event a lockedvacant unit is subsequently rented, a representative of the self-storagefacility must manually visit the unit and remove the lock. Such aprocess is burdensome, manually intensive, and increases the timebetween a customer renting a unit, and actually being able to access theunit.

Thus, there is a need in the self-storage industry for a system thatallows or disallows access to an over-locked storage unit, such as avacant storage unit, without the need for an on-site attendant. Such adistributed over-lock system would allow for immediate access to anover-locked storage unit, would encourage delinquent customers to bringan account current in a timely fashion, and would reduce operationalcosts associated with conventional electronic and standard combinationover-lock systems.

SUMMARY

In one embodiment, the invention is directed to a method for associatinglocks with unlock codes and lock identifiers, the method comprising:selecting a lock to be marked with a lock identifier and programmed withan unlock code, wherein the lock is not capable of electroniccommunication, wherein a database coupled to a processor stores unlockcodes and lock identifiers, the processor configured to: (i) randomlygenerate a plurality of unlock codes, (ii) randomly generate a pluralityof lock identifiers, (iii) create a plurality of unlock code/lockidentifier pairs by randomly selecting an unlock code from the pluralityof unlock codes, and randomly selecting a lock identifier from theplurality of lock identifiers, and (iv) select an unlock code/lockidentifier pair from the plurality of unlock code/identifier pairs,wherein the lock is marked with the selected lock identifier, andwherein the lock is programmed with the selected unlock code.

In another embodiment, the invention is directed to a method forrandomly generating unlock codes for locks, the method comprising:securing a location with a lock, wherein the lock is not capable ofelectronic communication, and wherein a database coupled to a processorstores an association of the lock and a customer, the processorconfigured to: (i) randomly generate a plurality of unlock codes, (ii)randomly generate a plurality of identifiers, (iii) create an unlockcode/identifier pair, wherein the unlock code/identifier pair is createdby randomly selecting an unlock code from the plurality of unlock codes,and randomly selecting an identifier from the plurality of identifiers,and (iv) associate the unlock code/identifier pair with the lock in thedatabase, wherein the processor is further configured to retrieve theunlock code associated with the lock from the database and transmit theunlock code to a mobile device associated with the customer.

In yet another embodiment, the invention is directed to a system forrandomly generating unlock codes for locks, the system comprising: alock not capable of electronic communication, a database configured tostore an association of the lock and customer information, the databasefurther configured to store a plurality of unlock code/identifier pairs,a processor communicatively coupled to the database, wherein theprocessor is configured to: (i) randomly generate a plurality of unlockcodes, (ii) randomly generate a plurality of identifiers, (iii) createthe plurality of unlock code/identifier pairs, wherein each unlockcode/identifier pair is created by randomly selecting an unlock codefrom the plurality of unlock codes, and randomly selecting an identifierfrom the plurality of identifiers, (iv) select an unlock code/identifierpair from the plurality of unlock code/identifier pairs, and (v)associate the selected unlock code/identifier pair with the lock in thedatabase; a mobile device communicatively coupled to the processor,wherein the mobile device is configured to transmit customer accountinformation to the processor; and a transceiver communicatively coupledto the processor, wherein the processor is further configured toretrieve the unlock code associated with the lock from the database uponreceipt of the customer information, and wherein the transceiver isconfigured to transmit the unlock code to the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other embodiments of the disclosure will be discussed withreference to the following exemplary and non-limiting illustrations, inwhich like elements are numbered similarly, and where:

FIG. 1 is a network architecture diagram of a distributed encryptedcombination over-lock and release system;

FIG. 2 is a flowchart illustrating the steps of encrypting an unlockcode for a combination over-lock;

FIG. 3 is a flowchart illustrating the steps of decrypting an unlockcode for a combination over-lock;

FIG. 4A is a perspective illustration of a combination over-lockaccording to an embodiment of the invention;

FIG. 4B is a perspective illustration of a combination over-lock with anidentifier tag according to an embodiment of the invention;

FIG. 4C is a perspective illustration of a combination over-lock with abarrel tumbler according to an embodiment of the invention;

FIG. 4D is a perspective illustration of an electronic over-lock with aninterface according to an embodiment of the invention;

FIG. 5 is a diagram of a kiosk and storage unit according to anembodiment of the invention;

FIG. 6A is an illustration of an over-lock release interface for asoftware application according to an embodiment of the invention;

FIG. 6B is an illustration of an over-lock release interface for asoftware application according to an embodiment of the invention;

FIG. 7 is a flow chat illustrating the steps of enabling and disablingan over-lock according to the embodiment of the invention;

FIG. 8 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code using the software application according to anembodiment of the invention;

FIG. 9 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code via a telephone call according to an embodimentof the invention;

FIG. 10 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code using the software application and only anaccount identifier according to an embodiment of the invention;

FIG. 11A is an illustration of an over-lock release interface thatreceives an account identifier for a software application according toan embodiment of the invention;

FIG. 11B is an illustration of an over-lock release interface thatreceives an account identifier for a software application according toan embodiment of the invention;

FIG. 12 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code via a telephone call using only an accountidentifier according to an embodiment of the invention;

FIG. 13 is a flowchart illustrating the steps taken to apply anover-lock to a vacant storage unit according to an embodiment of theinvention;

FIG. 14 is a flowchart illustrating the steps taken to retrieve anunlock code from a third-party property management system for anover-lock secured to a vacant storage unit according to an embodiment ofthe invention;

FIG. 15 is a flowchart illustrating the steps taken to retrieve anunlock code from a third-party property management system for anover-lock secured to a vacant storage unit according to an embodiment ofthe invention;

FIG. 16 is a flowchart illustrating the steps taken retrieve an unlockcode from the lock management system via electronic messaging using aserial number, according to an embodiment of the invention;

FIG. 17 is a flowchart illustrating the steps taken to retrieve anunlock code from the lock management system via electronic messagingusing an alphanumeric code, according to an embodiment of the invention;

FIG. 18 is a flowchart illustrating the steps of transmitting an unlockcode to a customer upon a customer account status changing fromdelinquent to non-delinquent, according to an embodiment of theinvention;

FIG. 19 is a flowchart illustrating the steps of transmitting an unlockcode to a customer upon a vacant storage becoming occupied, according toan embodiment of the invention; and

FIG. 20 is a flowchart illustrating the steps of randomly generatingunlock codes and identifiers, and randomly creating unlockcode/identifier pairs, according to an embodiment of the invention.

DETAILED DESCRIPTION

It should be understood that aspects of the invention are describedherein with reference to the figures, which show illustrativeembodiments. The illustrative embodiments herein are not necessarilyintended to show all embodiments in accordance with the invention, butrather are used to describe a few illustrative embodiments. Thus,aspects of the invention are not intended to be construed narrowly inview of the illustrative embodiments. In addition, the present inventionis an over-lock and release system. Although the system is describedwith respect to its application for self-storage facilities, it isunderstood that the system could be implemented in any setting where anover-lock system may be useful.

FIG. 1 is a network architecture diagram of a distributed encryptedcombination over-lock and release system. In an embodiment, the systemcan be implemented within a self-storage environment. The systemincludes a self-storage facility 102 coupled to a management site 118via a network 116. The management site 118 can be remote from theself-storage facility 102, and the management site 118 can servemultiple distributed self-storage facilities, such as in a centralmanagement site. The management site 118 can further be locatedoverseas, such as in a foreign call center.

In an embodiment, the management site 118 includes computing hardwareand software 119, consisting of a processing unit 120, a database 122,and a transceiver 124. The computing hardware and software 119 caninclude a server coupled to the network 116. In another embodiment, theprocessing unit 120 and database 122 can be cloud-based, and located ona server remote from the management site 118, such as on a serverprovided by Amazon Web Services® or the like. In an embodiment, theprocessor 120 and/or database 122 can be distributed systems, such asthat multiple distributed/cloud based units, structures, devices, orservers are utilized. In yet another embodiment, the database 122 is adatabase in which operational data is spread across different physicalor virtual locations, and comprises more than one cloud based databasesand/or data processing systems.

In another embodiment, the management site 118 can be located within thelocal vicinity of the self-storage facility 102, such as on-site. Themanagement site 118 can be a physical location with human personnel,such as a self-storage manager 108. In another embodiment, themanagement site 118 can be unmanned, and can include only the computinghardware and software 119. The network 116 may be any type of networksuitable to allow interaction between devices, such as a mobile device112 located at self-storage facility 102, and the computing hardware andsoftware 119 at the management site 118. For example, the network 116may be a wired network, a wireless network, or any combination thereof.Further, the network 116 may include a distributed computing network, anintranet, a local-area network (LAN) and/or a wide-area network (WAN),or any combination thereof. For example, the LAN may make use of WIFI inits many variations and the WAN may make use of broadband, cellularand/or satellite networks using technologies including, but not limitedto, CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT,DataTAC, Mobitex, EDGE and other 2G, 3G, 4G and LTE technologies.However, those of ordinary skill in the art will appreciate that thenetwork 116 is not limited thereto.

The self-storage facility 102 can include a storage unit 104, which canbe rented by a customer 106. As used herein, the term “customer” caninclude a renter, client, tenant, lessee, user, or an authorized agent.Although the invention will be described with respect to self-storagefacilities, the invention can be implemented in any setting where anover-lock system may be useful, such as hotel rooms, apartmentbuildings, storage containers, short-term housing rentals, and lockers.In addition, the invention can be implemented within a controlled accesssystem, such as for equipment rooms, vaults, hospitals, airports,government facilities, nuclear power facilities, water treatmentfacilities, weapon storage facilities, aircraft cockpits, and any othersetting that requires restricted, selective, or monitored access.

In the event that customer 106 becomes delinquent in the payment ofrent, the self-storage manager 108 can place an over-lock 110 on thestorage unit 104. The over-lock 110 is a secondary lock that is used toprevent the customer 106 from accessing the storage unit 104 until thedelinquent past due balance is paid by customer 106.

In a preferred embodiment, the over-lock 110 is a combination padlockthat requires an unlock code to be manually entered in order to open theover-lock 110. In another embodiment, the over-lock 110 can be deadbolt,knob lock, or lever lock that includes a combination mechanism. Thecombination mechanism can include a tubular barrel, a rotary knob,pushpins, or a mechanical keypad. In another embodiment, the over-lock110 can be an electronic lock that accepts a combination input viadigital keys or a touchscreen. In an embodiment, the over-lock 110 is alock with no electronic circuitry or electronic components, and theover-lock 110 is not capable of electronic communication with any remoteor local systems.

In an embodiment, the over-lock 110 can include an identifier, such as aserial number, unique code, barcode, QR code, or other unique indicia.In an embodiment, the identifier is engraved onto the over-lock 110. Inother embodiments, the identifier is affixed via a label to theover-lock 110, affixed to a tag that is attached to the over-lock 110,or otherwise imprinted, drawn, or engraved on the over-lock 110 or tag.

Upon payment of a delinquent past due balance by the customer 106, themanagement site 118 can enable the release of an unlock code for theover-lock 110. At this time, the customer 106 can use a mobile device112, such as their mobile phone, to access a software application 114created by the self-storage manager 108. The software application 114can be a proprietary program created and/or owned by the self-storagefacility 102, and which can be downloaded by the customer 106 from, forexample, a website operated by the self-storage manager 108, the AppleiTunes App Store®, the Android App Store®, and the like.

The software application 114 can allow bi-directional communicationbetween the mobile device 112 and the management site 118, self-storagemanager 108, processor 120, database 122, and/or transceiver 124.

In yet another embodiment, the software application 114 is a websiteaccessed via a Uniform Resource Locator (URL) using a browser on themobile device 112.

The mobile device 112 is not limited to a mobile phone, and can includetablets, wearable devices, personal digital assistants (PDAs), laptopcomputers, “smart” watches, “smart” glasses, and any other devicecapable of receiving input from the customer 106, and which is capableof being connected to the network 116.

The software application 114 includes an interface that allows thecustomer 106 to enter the identifier. The identifier is then transmittedfrom the mobile device 112 via a network 116 to the management site 118.The identifier is received by the transceiver 124, and routed to theprocessing unit 120. The processing unit 120 performs a decryptionand/or look-up operation in the database 122, and retrieves an unlockcode for the over-lock 110 that is associated with the identifier. Theunlock code is then transmitted by the transceiver 124 to the mobiledevice 112 via the network 116. The unlock code is subsequentlydisplayed to the customer 106 on the mobile device 112 via the softwareapplication 114. Upon receiving the displayed unlock code, the customer106 can then unlock the over-lock 110, and re-gain access to the storageunit 104.

FIG. 2 is a flowchart illustrating the steps of encrypting an unlockcode for a combination over-lock. In step 200, a unique identifier isgenerated for the over-lock 110. The identifier can be generated at thetime of manufacturing by the over-lock manufacturer, and can betransmitted with the over-lock 110 at the time of purchase by theself-storage facility. In this embodiment, the identifier can beengraved or permanently affixed to the over-lock 110.

In another embodiment, the identifier is generated by the self-storagefacility. In this embodiment, an algorithm on the processing unit 120randomly generates the identifier, or it can be generated manually bythe self-storage facility. In another embodiment, a third-partyover-lock provider can generate the identifier, and can sell or leasethe over-locks to a self-storage facility. The third-party over-lockprovider can manage the computing hardware and software 119 for theself-storage facility, and/or can lease the computing hardware andsoftware 119 to the self-storage facility.

In an embodiment, the identifier can be generated using an encryptiontechnique that utilizes the unlock code as an input. In addition,another identifying input can be utilized for the encryption along withthe unlock code, such as a self-storage facility identifier, federal taxidentification number, or a randomly generated string of characters.

In an embodiment, the identifier can be a string of numeric characters,alphabet characters, special characters, or a combination ofalphanumeric and/or characters. In addition, the identifier can includea portion identifying the self-storage manager 108, the self-storagefacility 102, and/or the customer 106.

In an embodiment where the identifier is a barcode, matrix code, a QRcode, or a similar scannable code, the identifier can be printed on theover-lock 110 at the time of manufacture, or alternatively, theidentifier can be printed on label and affixed to the over-lock 110 or atag attached to the over-lock 110 by either the manufacturer or theself-storage facility.

In another embodiment, the over-lock 110 or tag can have a digitallyimprinted code and/or microchip, such as a RFID or Bluetooth low energytransmitter. The customer 106 can be provided with a physical key fobthat can read the code sent from the microchip, and which can displaythe code to the user. The key fob can be implemented into a softwareapplication on the mobile device 112 as well. In this embodiment, theidentifier is not readily visible, which adds a layer of securityagainst the over-lock 110, and its corresponding unlock code, becomingknown over a period of time due to re-use.

In step 202, the unlock code is generated for the combination over-lock110. Again, the unlock code can be generated at the time ofmanufacturing by the over-lock manufacturer, and transmitted with theover-lock 110 at the time of purchase by the self-storage facility.

In another embodiment, the self-storage facility can generate the unlockcode for the over-lock 110. The unlock code can be randomly generated byan algorithm on the processing unit 120, or generated manually by theself-storage manager 108.

In an embodiment, the identifier and/or unlock code can be time-limited,and can expire after a pre-determined amount of time or on a certaindate. In this embodiment, the expired identifier and/or unlock code mustbe re-generated as per step 200 and 202 above.

In an embodiment, the unlock code can be generated using an encryptiontechnique that utilizes the identifier as an input. In addition, anotheridentifying input can be utilized for the encryption along with theidentifier, such as a self-storage facility identifier, federal taxidentification number, or a randomly generated string of characters.

In step 204, the processing unit 120 associates the identifier with theunlock code for the over-lock 110 using an encryption technique. Theencryption technique can include at least one of a hash function, a keyderivation function, a block cipher operation, and an obfuscationfunction. In addition, the encryption algorithm used by the processingunit 120 can include a Triple Data Encryption Standard (DES) algorithm,a RSA cryptosystem algorithm, a Blowfish cipher algorithm, a Twofishcipher algorithm, or an Advanced Encryption Standard (AES) algorithm.

In step 206, the encrypted identifier and unlock code pair is stored inthe database 122. The database 122 can be stored locally at themanagement site 118, can be located on a remote cloud-based server, orat another facility remote from the management site 118.

In yet another embodiment, each storage unit 104 can include a scannablecode, such as a barcode, located on a visible portion of its exterior.Each over-lock 110 can also include a barcode as its identifier, asdescribed above. Upon applying the over-lock to a storage unit 104, theself-storage manager 108 can scan both barcodes. These barcodes are thentransmitted to the processing unit 120, where the barcode pairs areassociated with each other and stored in the database 122.

FIG. 3 is a flowchart illustrating the steps of decrypting an unlockcode for a combination over-lock. In step 300, upon encountering anover-lock 110 on their storage unit 104, the customer 106 locates theidentifier on the over-lock 110. The customer 106 can enter theidentifier into a software application 114 on their mobile device 112,as described above. In an embodiment, the customer 106 can take apicture of the identifier and send it via text, SMS, MMS, email, orsecure message through the software application, to the management site118. In another embodiment, the customer 106 can initiate a live-streamor video chat of the identifier with the management site 118, using, forexample, Apple FaceTime®, Skype®, Snapchat®, or the like. In anotherembodiment, the identifier can be entered through a website accessed viaa URL using a browser on the mobile device 112.

In another embodiment, the customer 106 can scan a barcode, matrix code,a QR code, or a similar scannable code with a camera or optical pickupmeans on the mobile device 112. The scanned identifier is thentransmitted to the management site 118.

In yet another embodiment, the customer 106 can place a telephone callto the remote management site 106 and/or the self-storage manager 108and provide the identifier and/or their credentials verbally.

In an embodiment, prior to being able to access the software application114, the customer 106 must enter credentials, such as a login andpassword, or other indicia that verifies the customer's identity. Thecredentials may also be supplied via biometric means, such as withfingerprint, iris, voice, face, and gesture recognition meansincorporated into the mobile device 112 and/or software application 114.In another embodiment, the credential can include a one-time or limiteduse password provided by a secure token, such as a RSA SecurID®.

In another embodiment, the credentials may be transmitted along with theidentifier. In this embodiment, the credentials can include customer'smobile device number, login, password, email address, phone number,account number, personal identification number (PIN), name, driver'slicense number, social security number, birthdate, storage unit number,and/or a unique account identification code previously provided to thecustomer 106 by the self-storage facility and/or any combinationthereof.

In yet another embodiment, the customer 106 can designate authorizedparties who can request the unlock code as well. For example, acustomer's spouse, authorized agents, business associates, attorneys,and any other parties whom the customer 106 wishes to have access to thestorage unit 104 can have their credentials associated with the storageunit. In this embodiment, the database record for the storage unit 104and/or over-lock 110 includes a listing of all authorized parties andtheir respective credentials.

In step 302, the identifier, along with the credentials, if required,are transmitted to the management site 118 via the network 116. In anembodiment, the identifier is specifically transmitted to the computinghardware and software 119, which can be located at the management site118, or alternatively, located at a remote facility or servercommunicatively coupled to the management site 118.

As described above, the management site 118 and/or processing unit 120can be located remotely from the self-storage facility 102, and thus,the network 116 can include a WAN and utilize broadband, cellular,and/or satellite communication means. In another embodiment, theprocessing unit 120 can be located on-site at the self-storage facility102. In this embodiment, in addition to the aforementioned communicationmeans, the mobile device 112 can utilize a short-range communicationprotocol, such as Bluetooth®, infrared, ZigBee®, and/or opticalwireless, to communicate with the computing hardware and software 119.

In step 304, the processing unit 120 receives the identifier. Theprocessing unit 120 uses the identifier as an input to decrypt theunlock code. Various decryption techniques may be employed, and suchtechniques can include the use of private and public keys. In anotherembodiment, the decryption step involves performing a look-up operationin the database 122 to locate the over-lock record associated with theidentifier. Once the relevant record is located, the processing unit 120extracts the unlock code from the over-lock record. The look-upoperation can be standalone, or in addition to the decryption techniquesdescribed herein.

In another embodiment, the unlock code and identifier can both berandomly generated, either using an algorithm on a computing device, ormanually. The randomly generated unlock code and identifier can then belinked or associated with one another in a database, table, matrix,ledger, or the like. The linking/associating can be done randomly usingan algorithm on the computing device, or can be done manually.

In step 306, the unlock code is transmitted to the mobile device 114 viathe network 116 using a transceiver 124 coupled to the processor 120.Upon receipt by the mobile device 112, the software application 114displays the unlock code to the customer 106. In yet another embodiment,the unlock code can be transmitted to the mobile device 112 from themanagement site 118 via SMS, MMS, email, or video chat. In yet anotherembodiment, the self-storage facility can place a telephone call to thecustomer 106 and verbally provide the unlock code. In this embodiment,human personnel, such as the self-storage manager 108 at the managementsite 118, can place via an automated system or the telephone call.

FIG. 4A is a perspective illustration of a combination over-lockaccording to an embodiment of the invention. The combination over-lock110 includes an identifier 400, which can be engraved or otherwisepermanently affixed to the over-lock 110. In another embodiment, theidentifier 400 can be on a label affixed to the over-lock 110, such asan adhesive label. The identifier 400 can be located on an underside ofthe over-lock 110, as shown in FIG. 4A, or can be located on thefront-face, rear plate, or shackle.

FIG. 4B is a perspective illustration of a combination over-lock with anidentifier tag according to an embodiment of the invention. In thisembodiment, the identifier 400 is located on a tag 402 that is affixedto the over-lock 110. The tag 402 can be affixed to the shackle, thecombination knob, or alternatively, can be applied partially viaadhesive to any surface of the over-lock. The tag 402 can be placedwithin a weatherproof encasement (not shown).

FIG. 4C is a perspective illustration of a combination over-lock with abarrel tumbler according to an embodiment of the invention. In thisembodiment, the identifier 400 is a scannable code, such as a barcode,and is located on the front or rear surface of the over-lock 110. Theunlock code can be manually entered using the barrel tumbler 406 on theunderside of the over-lock 110. The over-lock 110 depicted in FIG. 4C isshown as an example, and various designs of locks having a barreltumbler, a rotary knob, push-pins, or a mechanical keypad can beutilized with this invention, such as combination input mechanism canalso be located on a side or front face of the over-lock 110.

FIG. 4D is a perspective illustration of an electronic over-lock with aninterface according to an embodiment of the invention. In thisembodiment, the over-lock 110 includes an interface, such as atouch-screen 408. The identifier 400 can be located on the casing 410 orshackle 412, or affixed to the over-lock 110 via a tag (not shown)similar to the embodiments shown in FIGS. 4A-4C. In another embodiment,the identifier 400 can be displayed on the touch-screen 408. Theelectronic over-lock 110 can function similarly to the mobile device114, and can include circuitry for accepting customer input and fortransmitting and receiving data from a remote source. In thisembodiment, the customer 106 can access the software application 116 viathe touch-screen 408, and can enter their credentials and theidentifier. The electronic over-lock 110 can then transmit theidentifier to the management site 118. Upon a successful decryption atthe management site 118, the unlock code is transmitted to the over-lock110, which is automatically unlocked without further customerintervention.

FIG. 5 is a diagram of a kiosk and storage unit according to anembodiment of the invention. In another embodiment, the storage unit 104can include a kiosk 500, either adjacent to the storage unit 104, orlocated at the self-storage facility 102. The kiosk 500 can functionsimilar to the mobile device 114, and allow the customer 106 to requestan unlock code. The kiosk 500 can accept an identifier from theover-lock 110, and can then transmit the identifier to the managementsite 118. Upon a successful decryption at the management site 118, theunlock code is transmitted for display at the kiosk 500. The kiosk 500can also perform other services and management functions for theself-storage facility 102, such as accepting payments, processingstorage unit rentals, providing voice and chat operations with theself-storage manager 108 and/or management site 118, and vendingaccessories.

In another embodiment, the customer 106 can utilize the kiosk 500 torequest an unlock code, and the unlock code is returned for display tothe mobile device 112, or vice-versa.

FIG. 6A is an illustration of an over-lock release interface for asoftware application according to an embodiment of the invention. Theunlock interface 600 can be displayed on the mobile device 112 once thecustomer 106 activates the software application 114. The unlockinterface 600 allows the customer 106 to enter an identifier for theover-lock 110 at input box 602. The unlock interface 600 can alsodisplay information 604 such as the customer name and facility name, andcustomer status 606. The customer status 606 can be either “current”(i.e., paid in full and in good standing), or “delinquent” (i.e., havinga past due balance). In an embodiment, the customer status 606 caninclude be “pending”, indicating that a payment has been submitted, butnot yet processed, such as in the case of wire transfers or digitalcurrency payments which typically require a delay in settlement.

In an embodiment, the unlock code 606 is displayed after the customer106 transmits the identifier by selecting the “SUBMIT” button 610, andafter the processing unit 120 successfully decrypts the unlock code.

In another embodiment, the interface 600 does not include the unlockcode 606, and the unlock code is transmitted to the customer 106 via atext, SMS, MMS, email, video chat, secure message via the softwareapplication, or telephone call.

FIG. 6B is an illustration of an over-lock release interface for asoftware application according to an embodiment of the invention. In theevent that the customer 106 has not made payment on a delinquent pastdue balance, and still attempts to retrieve the unlock code, thecustomer status 606 will be listed as “Delinquent”. In addition, the“SUBMIT” button 610 will be greyed our or inactive, so that the customer106 cannot submit the identifier. In another embodiment, the customer106 may not even reach the unlock interface 600, and rather, is directedtoward a billing webpage upon launching the software application 114,where they can make a payment to rectify their delinquent account (notshown).

FIG. 7 is a flow chat illustrating the steps of enabling and disablingan over-lock according to the embodiment of the invention. In step 700,the management site 118 determines if a customer account is delinquent.If the account is current and there is no outstanding past due balance,the process terminates at step 702 and no over-lock 110 is required. Theprocess continues back to step 700 where the customer account iscontinually monitored for delinquency by the management site 118.

If the customer account is delinquent, the process continues to step704, where an over-lock 110 is placed on the storage unit 104. Theover-lock 110, in a preferred embodiment, is manually placed over theprimary lock or latch, thereby preventing movement of the door hasp,even if the primary lock is removed.

In another embodiment, the customer 106 can have multiple storage unitson their account. If the customer 106 is delinquent on all or part oftheir account, all of the storage units on the customer's account can beover-locked. In another embodiment, only select storage units or asingle storage unit can be over-locked, based on the amount or extent ofdelinquency on the account.

In step 706, the processing unit 120 determines if the customer accountis still delinquent. If the account is still delinquent, the processingunit 120 disables the over-lock release function. In this scenario, theprocessing unit 120 prevents the over-lock release interface shown inFIG. 6B from returning an unlock code. In another embodiment, if thecustomer 106 attempts to request an unlock code via text message, email,video chat, or telephone call while having a delinquent past due accountstatus, the customer 106 will be informed by the self-storage facilitythat their account is delinquent, and they cannot retrieve the unlockcode.

If the customer's account is no longer delinquent in step 706, then theprocess continues to step 710, where the over-lock release is enabled bythe processing unit 120, and the customer 106 can retrieve the unlockcode in step 712. The process continues back to step 700 where thecustomer account is continually monitored either by the self-storagefacility.

FIG. 8 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code using the software application according to anembodiment of the invention. In step 800, the customer 106 discoversthat their storage unit 104 has been over-locked.

In step 802, the customer 106 follows instructions on a notice from theself-storage facility to access the software application 114 in order toretrieve an unlock code for the over-lock 110. In an embodiment, anotice, such as a hangtag, placard, sign, or other indica is placed onthe over-lock 110, adjacent to the over-lock 110, and/or on a door orframe of the storage unit. The notice can include instructions on how toaccess the software application 114. As discussed earlier, the softwareapplication 114 can be downloaded by the customer 106 from, for example,a website operated by the self-storage manager 108, the Apple iTunes AppStore®, the Android App Store®, and the like, or the softwareapplication 114 can be a website accessed via a URL using a browser onthe mobile device 112.

In an embodiment, the notice can instruct the user to launch thesoftware application 114 on their mobile device 112, can instruct theuser to visit a URL using a browser on their mobile device 112, and/orcan include a scannable code which automatically launches the softwareapplication 114 or a URL on the mobile device 112. In anotherembodiment, the notice can instruct the user to place a telephone callor send a message, such as a SMS, MMS, or email, to the self-storagefacility.

In another embodiment, the notice can be sent directly to the customer106, such as via text, SMS, MMS, email, or secure message through thesoftware application. The notice can include a URL or other mechanism tolaunch the software application 114 on the mobile device 112. Inaddition, the notice can be mailed via physical mail to the customer'saddress on file.

In yet another embodiment, the notice can be a telephone call from themanagement site 118, instructing the customer 106 to access the softwareapplication 114.

In step 804, the customer 106 is prompted to enter their credentials,such as a login and password, or other indicia that verifies thecustomer's identity. The credentials may also be supplied via biometricmeans, such as with fingerprint, iris, voice, face, and gesturerecognition means incorporated into the mobile device 112 and/orsoftware application 114. In another embodiment, the credential caninclude a one-time or limited use password provided by a secure token,such as a RSA SecurID®.

In step 806, the management site 118 determines if the credentials arevalid. If not, the process returns to step 804, and the customer 106 isprompted to re-enter their credentials. If the credentials are deemedvalid, then in step 808, the management site 118 determines if thecustomer's account is indeed delinquent. If the customer 106 no longerhas a past due balance, then the customer 106 is prompted to enter theidentifier from the over-lock 110 in step 810. This scenario may occur,for example, if a customer 106 makes a payment to rectify a past duebalance from a remote location, such as their home or work, and thensubsequently arrives at the self-storage facility to discover apreviously placed over-lock 110.

If the customer 106 still has a past due balance, then the customer 106is prompted to pay their past due balance in step 812. In an embodiment,the customer 106 can make payments to the self-storage facility via acredit card, debit card, automated clearing house (ACH) transfer, andwire transfer. The software application 114 may allow the user to storea payment method on file, such as a stored credit card, or a linked bankaccount.

In addition, the self-storage facility can accept payment viathird-party payment processing systems, such as PayPal®, Stripe®, ApplePay®, Android Pay®, Square®, Amazon Payments®, Viewpost®, and othersimilar platforms. Such payment processing systems can be integratedwithin the software application 114.

In yet another embodiment, the self-storage facility can accept paymentvia cryptographic and digital currencies, such as, but not limited toBitcoin, Ethereum, Litecoin, and Nano.

In another embodiment, the customer 106 can visit the managerself-storage and/or the remote management site 118 and pay the past duebalance in-person.

The process then returns to step 808, where the management site 118determines if the customer 106 still has a past due balance on theiraccount. If there is no past due balance, then the customer 106 isprompted to enter the identifier from the over-lock 110 in step 810. Ifthe customer 106 still has a past due balance, then the process returnsto step 812 where the customer 106 is prompted to pay their past duebalance.

In step 814, the management site 118 transmits the unlock code to thecustomer 106, who can then remove the over-lock 110 from their storageunit 104.

FIG. 9 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code via a telephone call according to an embodimentof the invention. In step 900, the customer 106 discovers that theirstorage unit 104 has been over-locked.

In step 902, the customer 106 follows instructions on a notice from theself-storage facility to call the management site 118 in order toretrieve an unlock code for the over-lock 110. In an embodiment, themanagement site 118 can include a self-storage manager 108, call center,representative, or third-party answering service. In another embodiment,the customer 106 can send a message to the management site 118, such asvia text, SMS, MMS, email, or secure message through the softwareapplication in order to schedule a call from the management site 118.

In step 904, the management site 118 requests the customer 106 toprovide credentials, as described above.

In step 906, the management site 118 determines if the credentials arevalid. If not, the process returns to step 904 and the management site118 requests the customer 106 to provide their credentials again. If thecredentials are deemed valid, then in step 908, the management site 118determines if the customer's account is indeed delinquent. If thecustomer 106 no longer has a past due balance, then the customer 106 isprompted to enter the identifier from the over-lock 110 in step 910. Thecustomer 106 can verbally provide the identifier, enter the identifiervia their alpha-numeric keypad on their mobile device 112, or scan theidentifier and transmit it to the management site 118 using their mobiledevice 112.

If the customer 106 still has a past due balance, then the customer 106is prompted to pay their past due balance in step 912.

The process then returns to step 908, where the management site 118determines if the customer 106 still has a past due balance on theiraccount. If there is no past due balance, then the customer 106 isprompted to provide the identifier from the over-lock 110 in step 910.If the customer 106 still has a past due balance, then the processreturns to step 912 where the customer 106 is prompted to pay their pastdue balance.

In step 914, the management site 118 provides the unlock code to thecustomer 106, who can then remove the over-lock 110 from their storageunit 104.

In an embodiment, the over-lock 110 can include an emergency mode, whereemergency personnel, such as first responders, police, firefighters, andemergency medical service providers and request an unlock code. In thisembodiment, the emergency personnel can transmit an emergency credentialalong with the identifier. Upon receipt of the emergency credential bythe management site 118, the processing unit 120 foregoes credentialverification and proceeds with decrypting the unlock code.

In yet another embodiment, the over-lock 110 is an electronic lock thataccepts a combination input via digital keys or a touchscreen. Thecustomer 106 can be provided with a secure token that provides aone-time or limited use password, such as the RSA SecurID®. In the eventof a delinquent past due balance, the management site 118 can remotelydisable the secure token until the customer 106 makes a payment of thepast due balance.

In another embodiment, the entire process of retrieving an unlock codeby the customer 106 can be automated. For example, the management site118 can include an automated attendant that verifies the identity of thecustomer 106 via the means described above, receives the identifier fromthe customer 106, and provides the unlock code to the customer 106. Theprocess can also occur in an automated fashion without humanintervention from the self-storage facility or management site 118 viathe kiosk 500.

FIG. 10 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code using the software application and a customeraccount identifier according to an embodiment of the invention.

In step 1000, the customer 106 discovers that their storage unit 104 hasbeen over-locked.

In step 1002, the customer 106 follows instructions on a notice from theself-storage facility to access the software application 114 and/or website in order to retrieve an unlock code for the over-lock 110 asdescribed herein.

In step 1004, the customer 106 is prompted to enter their credentials,such as the customer's mobile device number, email address, login,password, phone number, account number, personal identification number(PIN), name, driver's license number, social security number, birthdate,and/or a unique account identification code. The over-lock identifierand/or unlock code is previously associated with the storage unit and/orcustomer.

The unlock code and/or over-lock identifier can be previously associatedwith the storage unit and/or the customer. This association can be inthe form of a mapping table in the database 122. In one embodiment, atthe time of placing the over-lock on the storage unit 104, the unlockcode for the over-lock is mapped to the storage unit 104 and/or customerrecord in the database 122. During a subsequent lookup, the storage unit104 or customer information is required by the processing unit 120 toretrieve the unlock code. In this embodiment, the unlock code andstorage unit 104 and/or customer information may or may not beencrypted.

In another embodiment, the over-lock identifier is generated using anencryption technique using the unlock code. The over-lock identifier canthen be associated with an over-lock, and/or can be associated with thestorage unit 104 and/or customer. In the event that the over-lockidentifier is associated with the storage unit 104 and/or customer, thenthe storage unit 104 and/or customer are also associated with thecorresponding over-lock in the database 122. During a subsequent lookup,the over-lock identifier is required by the processing unit 120 in orderto decrypt the unlock code.

In step 1006, the management site 118 determines if the credentials arevalid. If not, the process returns to step 1004, and the customer 106 isprompted to re-enter their credentials. If the credentials are deemedvalid, then in step 1008, the customer is prompted to enter an accountidentifier. In this embodiment, the management site 118 receives thecustomer account identifier, and the management site 118 does notnecessarily receive a serial number or unique identifier of theover-lock itself. The account identifier can include, but is not limitedto, a storage unit/unit number, an account number, and any otheridentifier that associated the customer with a specific account orstorage unit or units. The management site 118 performs a look-upfunction using the account identifier. The look-up function correlatesthe account identifier with the storage unit 104, the over-lockidentifier and/or the unlock code, as well as a customer account.

In step 1010, based on the look-up, the management site 118 determinesif the customer account is delinquent. If the customer 106 still has apast due balance, then the customer 106 is prompted to pay their pastdue balance in step 1012 as described herein. If there is no past duebalance, then the management site 118 transmits the unlock code to thecustomer 106 in step 1014, who can then remove the over-lock 110 fromtheir storage unit 104.

If the customer 106 still has a past due balance in step 1010, then thecustomer 106 is prompted to pay their past due balance in step 1012 byany of the means described herein.

FIG. 11A is an illustration of an over-lock release interface thatreceives an account identifier for a software application according toan embodiment of the invention. The unlock interface 600 can bedisplayed on the mobile device 112 once the customer 106 activates thesoftware application 114. The interface 600 is displayed after thecustomer 106 has entered their credentials and has been verified by themanagement site 118. The unlock interface 600 allows the customer 106 toenter a customer account identifier, such as, for example, their storageunit number, at input box 602. The unlock interface 600 can also displayinformation 604 such as the customer name and facility name afterreceiving the customer account identifier, and customer status 606. Thecustomer status 606 can be either “current” or “active” (i.e., paid infull and in good standing), or “delinquent” (i.e., having a past duebalance). In an embodiment, the customer status 606 can include be“pending”, indicating that a payment has been submitted, but not yetprocessed, such as in the case of wire transfers or digital currencypayments which typically require a delay in settlement.

In an embodiment, the unlock code 608 is displayed after the customer106 transmits the identifier by selecting the “SUBMIT” button 610, andafter the processing unit 120 successfully decrypts the unlock code. Ifan over-lock identifier was previously associated with the storage unit,the processing unit 120 can perform a lookup of the over-lock identifierand perform the decryption step, as described previously herein. In theevent that the unlock code was previously associated with the storageunit, then the processing unit 120 performs a lookup of the storage unitto retrieve the associated unlock code.

FIG. 11B is an illustration of an over-lock release interface thatreceives an account identifier for a software application according toan embodiment of the invention. In the event that the customer 106 hasnot made payment on a delinquent past due balance, and still attempts toretrieve the unlock code, the customer status 606 will be listed as“Delinquent”. In addition, the “SUBMIT” button 610 will be greyed our orinactive, so that the customer 106 cannot submit the identifier. Inanother embodiment, the customer 106 may not even reach the unlockinterface 600, and rather, is directed toward a billing webpage uponlaunching the software application 114, where they can make a payment torectify their delinquent account (not shown).

FIG. 12 is a flowchart illustrating the steps taken by a customer toretrieve an unlock code via a telephone call using only an accountidentifier according to an embodiment of the invention. In step 1200,the customer 106 discovers that their storage unit 104 has beenover-locked.

In step 1202, the customer 106 follows instructions on a notice from theself-storage facility to call the management site 118 in order toretrieve an unlock code for the over-lock 110. In an embodiment, themanagement site 118 can include a self-storage manager 108, call center,representative, or third-party answering service. In another embodiment,the customer 106 can send a message to the management site 118, such asvia text, SMS, MMS, email, or secure message through the softwareapplication in order to schedule a call from the management site 118.

In step 1204, the management site 118 requests the customer 106 toprovide their credentials, as described herein.

In step 1206, the management site 118 determines if the credentials arevalid. If not, the process returns to step 1204, and the customer 106 isprompted to re-provide their credentials. If the credentials are deemedvalid, then in step 1208, the customer is prompted to enter an accountidentifier. In this embodiment, the management site 118 receives thecustomer account identifier, and the management site 118 does notnecessarily receive a serial number or unique identifier of theover-lock itself. The account identifier can include, but is not limitedto, a storage unit/unit number, an account number, and any otheridentifier that associated the customer with a specific account orstorage unit or units. The management site 118 performs a look-upfunction using the account identifier. The look-up function correlatesthe account identifier with the storage unit 104, the over-lockidentifier, and/or the unlock code, as well as a customer account. In anembodiment, multiple customer accounts, or multiple individualsassociated with a customer account, can be associated with the storageunit 104, the over-lock identifier, and/or the unlock code.

If there is no past due balance, then the management site 118 transmitsthe unlock code to the customer 106 in step 1214, who can then removethe over-lock 110 from their storage unit 104.

If the customer 106 still has a past due balance, then the customer 106is prompted to pay their past due balance in step 1212. The process thenreturns to step 1210, where the management site 118 determines if thecustomer 106 still has a past due balance on their account.

FIG. 13 is a flowchart illustrating the steps taken to apply anover-lock to a vacant storage unit. In step 1300, the self-storagefacility applies an over-lock to a vacant storage unit. In step 1302,the over-lock identifier is assigned, mapped, associated with, or linkedto the specific vacant storage unit in a database coupled to a lockmanagement system operated by the management site. In an embodiment, theover-lock identifier and/or the unlock code for the over-lock are mappedto the specific vacant storage unit in the database.

As discussed above, the management site can be separate from theself-storage facility, and can be owned and/or operated by an entitydifferent from the self-storage facility. In an embodiment, theself-storage facility is a customer of the management site, andpurchases a subscription, license, or the like to the lock managementsystem, from the management site.

In step 1304, the unlock code is transmitted from the lock managementsystem to a third-party property management system via an applicationprogramming interface (API). In an embodiment, the third-party propertymanagement system is owned and/or operated by an entity different fromthe management site and/or the self-storage facility. The third-partyproperty management system can be, but is not limited to, softwareoffered by, for example, storEDGE®, SiteLink®, Storage Commander®,QuikStor®, 6Storage®, Tredds Self Storage®, Easy Storage Solutions®,Convoyant ResNexus®, and the like.

The API allows the lock management system to communicate with thethird-party property management system, and allows either unidirectionalor bidirectional transmission of data between the two systems.

In an embodiment, the lock management system is a completely separateand distinct software program from the third-party property managementsystem. The lock management system and the third-party propertymanagement system can be located on different servers, and only coupledvia the API, and not by any direct, physical network communicationlinks. Furthermore, the lock management system can integrate withvarious different third-party property management systems via multipleAPIs, such that a single lock management system can communicate withmultiple different, disparate third-party property management systems.

FIG. 14 is a flowchart illustrating the steps taken to retrieve anunlock code from a third-party property management system for anover-lock secured to a vacant storage unit. In step 1400, a customerarrives at a vacant storage unit that is secured with an over-lock. Inan embodiment, the storage unit or over-lock includes a notice that hasinstructions for the customer on how to request an unlock code for theover-lock.

The notice can instruct the user to launch a software application ontheir mobile device, and/or can instruct the user to visit a portal forthe lock management system using, for example, a URL on a browser ontheir mobile or computing device, and/or can include a scannable codewhich automatically launches the software application or a URL on theirmobile device. In another embodiment, the notice can instruct the userto place a telephone call or send a message, such as a SMS, MMS, oremail, to the self-storage facility or management site.

In another embodiment, the notice can be sent directly to the customervia text, SMS, MMS, email, or secure message through the softwareapplication, such that the customer does not physically have to visitthe vacant storage unit to view the notice. The notice can include a URLor other mechanism to launch the software application on their mobiledevice. In addition, the notice can be mailed via physical mail to thecustomer's address on file.

In step 1402, the customer accesses the lock management system portal,which is described in more detail above and depicted in FIGS. 11A and11B. Further in step 1402, the customer is prompted to enter theircredentials, such as the customer's mobile device number, email address,login, password, phone number, account number, personal identificationnumber (PIN), name, driver's license number, social security number,birthdate, and/or a unique account identification code.

In step 1404, the lock management system transmits the customercredential(s) and a storage unit identifier and/or over-lock identifierto the third-party property management system via the API. This stepdoes not require human or manual intervention or action; the lockmanagement system automatically and seamlessly transmits the customercredential(s) after receiving them from the customer via the portal.

In step 1406, the third-party property management system determines ifthe customer is truly a verified renter of that specific storage unit.If not, the customer request for the unlock code is denied in step 1408.

If, however the customer is a verified renter of that specific storageunit, the process continues to step 1410 where the third-party propertymanagement system determines if the customer's account is delinquent. Ifthe customer's account is not current and there is an outstanding pastdue balance, the process continues to step 1412 where the customer isprompted to make a payment to rectify their past due balance, asdiscussed in more detail above. The process can then return to step 1410where the customer's account status is once again verified.

If the customer's account is current and there is no outstanding pastdue balance, then the process continues to step 1414 where thethird-party property management system transmits the unlock code to thecustomer. In an embodiment, the unlock code can be transmitted to thecustomer via text, SMS, MMS, email, secure message through the softwareapplication, displayed on the customer's browser, or via an automatedtelephone call. Again, this step does not require human or manualintervention or action on the part of the self-storage facility,management site, or third-party property management system provider.

FIG. 15 is a flowchart illustrating the steps taken to retrieve anunlock code from a lock management system for an over-lock secured to avacant storage unit. In this embodiment, the process is similar to thesteps described above for FIG. 14 . However, in step 1500, thethird-party property management system can transmit the customer'scontact information, such as their mobile phone number, email address,and the like, to the lock management system via the API. In step 1502,the lock management system transmits the unlock code to the customer. Inan embodiment, the unlock code can be transmitted to the customer viatext, SMS, MMS, email, secure message through the software application,displayed on the customer's browser, or via an automated telephone call.Again, this step does not require human or manual intervention or actionon the part of the self-storage facility, management site, orthird-party property management system provider.

In an alternative embodiment, in lieu of either steps 1414 of FIG. 14 or1502 of FIG. 15 , the unlock code can be transmitted to the self-storagefacility manager or operator, or to a human operator at the managementsite, who can be then provide the unlock code to the customer via aphone call or in person, or via text, SMS, MMS, email, or secure messagethrough the software application.

In an embodiment, the lock management system is executed on thecomputing hardware and software 119, and operated by the management site118. In another embodiment, the lock management system can be acloud-based system, and located on a server remote from the managementsite 118, such as on a server or distributed server environment providedby Amazon Web Services® or the like.

FIG. 16 is a flowchart illustrating the steps taken to retrieve anunlock code from the lock management system via electronic messagingusing a serial number, according to an embodiment of the invention. Instep 1600, the customer 106 transmits an electronic message containingan over-lock identifier, such as a serial number, to the lock managementsystem. In an embodiment, the customer 106 uses their mobile device 112to send a text message containing the serial number to the lockmanagement system. The electronic message may be in any form, and may bea text message, SMS, MMS, email, or secure message through the softwareapplication. In an embodiment, the over-lock identifier can be a serialnumber, unique code, barcode, QR code, or other unique indicia.

In yet another embodiment, the customer 106 can take a photograph orimage of the over-lock identifier, and transmit the image to the lockmanagement system via their mobile device 112. Upon receipt, imageanalysis is performed by the lock management system and the over-lockidentifier is extracted from the photograph.

In yet another embodiment, the over-lock identifier is contained withina QR code. When the customer 106 scans the QR code with their mobiledevice 112, the software application on the mobile device 112 is causedto automatically execute a routine that transmits the QR code andcustomer credentials to the lock management system.

In step 1602, the lock management system receives the electronicmessage, and identifies the customer 106. In an embodiment, the lockmanagement system determines the identity of the customer 106 using atelephone number caller identification system (i.e., a “caller ID”system). In another embodiment, if the electronic message is transmittedusing a secure message through the software application, the credentialsof the customer 106 are transmitted to the lock management system alongwith, or as part of, the secure message. Once the customer 106 isidentified, the lock management system retrieves customer informationassociated with the customer 106.

In another embodiment, once the lock management system receives theelectronic message containing the serial number, the lock managementsystem transmits a message to the customer 106 requesting that thecustomer 106 provides their account credentials, such as a login orusername, or other indicia that verifies the customer's identify. Uponreceiving the credentials from the customer 106, the lock managementsystem can transmit another message to the customer 106 requesting thepassword for the account. If the customer 106 successfully responds witha valid password, the lock management system then proceeds to step 1604.

If, however, in step 1602, the customer does not respond with a validpassword, or does not provide valid credentials, the lock managementsystem transmits an electronic message containing an error message tothe customer 106. In an embodiment, the electronic message can include ahyperlink that allows the customer 106 to register for, or purchase,access to the location.

In step 1604, after the customer 106 is identified, the lock managementsystem determines if the customer 106 is associated with the serialnumber in the database 122. In an embodiment, the lock management systemperforms a look-up function using the customer information, such as thecustomer name, account identifier, PIN, driver's license number, socialsecurity number, birthday, and/or a unique account identification code.

If the lock management system determines that the customer 106 haspreviously been associated with the serial number, then the processcontinues to step 1606.

In another embodiment, the lock management system first identifies theover-lock that is associated with the serial number, and then determinesif the customer 106 has previously been associated with that over-lock.

In step 1606, the lock management system determines if the customer 106has a delinquent account. If the customer 106 has a past due balance,then the customer 106 is prompted to pay their past due balance in step1608 as described herein with regards to step 1012 in FIG. 10 . Theprocess then returns to step 1606 where the lock management system againdetermines if the customer 106 has a delinquent balance.

If, in step 1606, the lock management system determines that thecustomer 106 does not have a delinquent account or past due balance,then the lock management system retrieves an unlock code associated withthe over-lock and/or serial number in step 1610, and the lock managementsystem transmits an electronic message containing the unlock code to thecustomer 106 in step 1612. In an embodiment, the lock management systemtransmits the electronic message to the mobile device 112 via text, SMS,MMS, email, or secure message through the software application.

In another embodiment, the lock management system can place an automatedtelephone call to the mobile device 112, and the unlock code is read tothe customer 106 via a text-to-speech function. Alternatively, humanpersonnel, such as the self-storage manager 108 at the management site118, or a call center employee, is prompted to call the mobile device112 and provide the unlock code to the customer 106.

If, however, in step 1604, the lock management system determines thatthe customer 106 is not associated with the serial number, then in step1614, the lock management system transmits an electronic messagecontaining an error message to the customer 106. In an embodiment, theelectronic message can include a hyperlink that allows the customer 106to register for, or purchase, access to the location.

FIG. 17 is a flowchart illustrating the steps to retrieve an unlock codefrom the lock management system via electronic messaging using analphanumeric code, according to an embodiment of the invention. In step1700, the customer 106 transmits an electronic message containing analphanumeric code to the lock management system. In an embodiment, thealphanumeric code can consist of all letters, all numbers, all emojis,or a combination of numbers, letters, and or emojis. In an embodiment,the customer 106 uses their mobile device 112 to send a text messagecontaining the alphanumeric code to the lock management system. Theelectronic message may be in any form, and may be a text message, SMS,MMS, email, or secure message through the software application.

For example, the customer 106 can text the alphanumeric code “CODE” tothe lock management system. In an embodiment, the alphanumeric code canbe pre-determined by the lock management system, or alternatively, thealphanumeric code can be pre-determined by the customer 106. In yetanother embodiment, the alphanumeric code has a time expiration, suchthat after a period of time, such as, for example, 30 days, thealphanumeric code is reset by the lock management system.

In another embodiment, the customer 106 can speak the alphanumeric code(if it does not contain emojis), and the mobile device 112 can generatea voice-to-text message that is transmitted to the lock managementsystem in the form of an electronic message.

In step 1702, the lock management system receives the electronicmessage, and identifies the customer 106. In an embodiment, the lockmanagement system determines the identity of the customer 106 using acaller ID system, as described herein with regards to step 1602 in FIG.16 .

In step 1704, after the customer 106 is identified using the caller IDsystem, the lock management system retrieves all of the serial numbersand unlock codes associated with the customer 106. In this embodiment,the customer 106 may be associated with multiple over-locks.

If the customer 106 is associated with multiple over-locks, the customer106 can associate certain individuals, such as personnel of the customer106, friends, family members, and the like, with certain over-locks. Inthis manner, the customer 106 can provide selective access to unlockcodes to certain individuals for specific over-locks. Each individualcan have a unique alphanumeric code which is associated with thespecific over-locks that the customer 106 has granted them access to.Alternatively, every customer or customer personnel can use the samealphanumeric code, and each individual is then authenticated asdescribed herein with regards to step 1702.

In step 1706, the lock management system determines if the customer 106has a delinquent account. If the customer 106 has a past due balance,then the customer 106 is prompted to pay their past due balance in step1708 as described herein with regards to step 1012 in FIG. 10 . Theprocess then returns to step 1706 where the lock management system againdetermines if the customer 106 has a delinquent balance.

If, in step 1706, the lock management system determines that thecustomer 106 does not have a delinquent account or a past due balance,then the lock management system transmits an electronic messagecontaining the serial number(s) and respective unlock code(s) to thecustomer 106 in step 1710. In an embodiment, the lock management systemtransmits the electronic message to the mobile device 112 via text, SMS,MMS, email, or secure message through the software application.

In an embodiment, if the customer 106 is associated with multipleover-locks, then the lock management system can transmit a singleelectronic message to the customer 106 that contains each serial numberand unlock code pair for each over-lock. Alternatively, the lockmanagement system can transmit a separate electronic message to thecustomer 106 for each serial number and unlock code pair (i.e., aseparate electronic message for each over-lock is transmitted to thecustomer 106).

In yet another embodiment, if the customer 106 is associated withmultiple over-locks, the lock management system can transmit a list ofthe serial numbers for these over-locks, and the customer 106 can selectwhich serial number(s) it wishes to retrieve the unlock code(s) for.

In yet another embodiment, the alphanumeric code can be an identifierfor a specific over-lock location. For example, the over-lock can beassociated with a specific physical location. In an exemplaryembodiment, the customer 106 can text the identifier, such as “A11”,which can correspond to the location “Server Closet A11”, to the lockmanagement system in step 1700. The process continues as describedabove, and the lock management system in step 1704 determines if aserial number is in fact associated with this location. If a serialnumber is associated with the location, then the respective unlock codeis retrieved by the lock management system from the database 122. Theprocess continues, and in step 1706, the lock management systemtransmits the unlock code to the customer 106.

The identifier to the specific over-lock location can be pre-determinedby the lock management system and/or the customer 106.

FIG. 18 is a flowchart illustrating the steps of transmitting an unlockcode to a customer 106 upon a customer account status changing fromdelinquent to non-delinquent, according to an embodiment of theinvention. In step 1800, the lock management system queries thethird-party property management system. As discussed herein, the lockmanagement system can be communicatively coupled to the propertymanagement system via an API. In an embodiment, the lock managementsystem queries the property management system to determine if a customerhas a delinquent account. This determination can be made in a number ofways known to a person of ordinary skill in the art, and can include,but is not limited to, the use of a delinquent/non-delinquent flag,reading an account ledger balance, a gate access permission, and thelike. In an embodiment, the lock management system can transmit a queryto the property management system, and the property management systemreturns a value, message, and the like that indicates whether or not thecustomer has a delinquent account.

In an embodiment, the lock management system can query the propertymanagement system based on pre-determined intervals, such as, forexample, every day, once a week, bi-weekly, monthly, quarterly, yearly,and the like. In another embodiment, the lock management system canquery the property management system on a random basis. In anotherembodiment, the lock management system can query the property managementsystem on a constant, or semi-constant, basis, such as, for example,every second, every minute, every hour, and the like.

In yet another embodiment, the lock management system can receive areal-time notification from the property management system when acustomer account status changes from delinquent to non-delinquent, andvice-versa.

In step 1802, if the lock management system determines that the customerdoes not have a delinquent account, then the process returns to step1800 where the lock management system continues to query the propertymanagement system based on the pre-determined interval. If, however, thelock management system determines that the customer has a delinquentaccount, then in step 1804, the lock management system sets a delinquentflag (or any other type of indicator) in the database 122.

In step 1806, the lock management system again queries the propertymanagement system and determines if the customer still has a delinquentaccount. If the customer no longer has a delinquent account in step1806, which indicates that the account status has changed fromdelinquent in step 1802 to non-delinquent in step 1806, then the processcontinues to step 1808.

If, however, the lock management system determines that the customerstill has a delinquent account in step 1806, then the process returns tostep 1800.

In step 1808, the lock management system determines if the locationassociated with the customer's account is secured by an over-lock. Ifthe location is not secured by an over-lock, the process ends. If,however, the location is secured by an over-lock, then in step 1810, thelock management system retrieves the unlock code associated with theparticular over-lock, retrieves the contact information for the customerfrom the property management system, and transmits an electronic messagecontaining the unlock code to the customer. In an embodiment, thecontact information can include the customer's mobile phone number,email address, and the like. In an embodiment, the lock managementsystem transmits the electronic message to the mobile device 112 viatext, SMS, MMS, email, or secure message through the softwareapplication.

FIG. 19 is a flowchart illustrating the steps of transmitting an unlockcode to a customer 106 upon a vacant storage becoming occupied,according to an embodiment of the invention. In step 1900, the lockmanagement system queries the third-party property management system. Asdiscussed herein, the lock management system can be communicativelycoupled to the property management system via an API. In an embodiment,the lock management system queries the property management system todetermine if a particular location, such as a storage unit, is vacant oroccupied. This determination can be made in a number of ways known to aperson of ordinary skill in the art, and can include, but is not limitedto, the use of a vacant/occupied flag, or another indicator which isstored, maintained, or updated by the property management system. In anembodiment, the lock management system can transmit a query to theproperty management system, and the property management system returns avalue, message, and the like that indicates whether the location isvacant or occupied.

In an embodiment, the lock management system can query the propertymanagement system based on pre-determined intervals, such as, forexample, every day, once a week, bi-weekly, monthly, quarterly, yearly,and the like. In another embodiment, the lock management system canquery the property management system on a random basis. In anotherembodiment, the lock management system can query the property managementsystem on a constant, or semi-constant, basis, such as, for example,every second, every minute, every hour, and the like.

In yet another embodiment, the lock management system can receive areal-time notification from the property management system when alocation status changes from vacant to occupied, and vice-versa.

In step 1902, if the lock management system determines that the locationis not vacant, then the process returns to step 1900 where the lockmanagement system continues to query the property management systembased on the pre-determined interval. If, however, the lock managementsystem determines that the location is vacant, then in step 1904, thelock management system sets a vacant flag (or any other type ofindicator) in the database 122.

In step 1906, the lock management system again queries the propertymanagement system and determines if the location is still vacant. If thelocation is not vacant in step 1906, which indicates that the locationhas gone from being vacant in step 1902 to now being occupied in step1906, then the process continues to step 1908.

If, however, the lock management system determines that the location isstill vacant in step 1906, then the process returns to step 1900.

In step 1908, the lock management system determines if the location issecured by an over-lock. If the location is not secured by an over-lock,the process ends. If, however, the location is secured by an over-lock,then in step 1910, the lock management system retrieves the unlock codeassociated with the particular over-lock, determines the customerassociated with the over-lock and/or location, retrieves the contactinformation for the customer from the property management system, andtransmits an electronic message containing the unlock code to thecustomer. In an embodiment, the contact information can include thecustomer's mobile phone number, email address, and the like. In anembodiment, the lock management system transmits the electronic messageto the mobile device 112 via text, SMS, MMS, email, or secure messagethrough the software application.

FIG. 20 is a flowchart illustrating the steps of randomly generatingunlock codes and identifiers, and randomly creating unlockcode/identifier pairs, according to an embodiment of the invention. Instep 2000, the computing device randomly generates a plurality of unlockcodes. In step 2002, the computing device randomly generates a pluralityof identifiers. The generation of the random unlock codes andidentifiers can occur in a step-wise manner (i.e., the unlock codes arefirst generated, and then the identifiers are generated, or vice-versa).In another embodiment, the generation of the random unlock codes andidentifiers can occur in a staggered manner (i.e., a fixed or randomnumber of unlock codes are generated, and then a fixed or random numberof identifiers are generated, or vice-versa), until a predeterminednumber of unlock codes and identifiers are generated.

In an embodiment, the unlock codes and identifiers are randomlygenerated using a random number generator, function, or algorithm storedon the computing device and executed by software. The software caninclude, for example, software for the lock management system or theproperty management system, or a standalone software plug-in,application, or code.

In another embodiment, the unlock codes and identifiers are randomlygenerated using a manual process, and not generated using the computingdevice.

The computing device can be, for example, the computing hardware andsoftware 119, the processing unit 120, a cloud-based system, a server,or a distributed server environment, such as that provided by Amazon WebServices® or the like.

In an embodiment, once the random unlock codes and identifiers aregenerated, they can be temporarily stored in a buffer, database, table,matrix, ledger, random access memory, volatile memory, or the like.

Next, in step 2004, the computing device randomly creates pairs ofunlock codes and identifiers, or unlock code/identifier pairs, byrandomly selecting an unlock code from the plurality of unlock codes andrandomly selecting an identifier from the plurality of identifiers. Inan embodiment, the computing device uses a random link generator,function, or algorithm stored on the computing device and executed bysoftware to create the unlock code/identifier pairs. The software caninclude, for example, software for the lock management system or theproperty management system, or a standalone software plug-in,application, or code.

In another embodiment, the unlock codes and identifiers are randomlypaired using a manual process, and not associated using the computingdevice.

In step 2006, each unlock code/identifier pair is associated with anover-lock. In an embodiment, the computing device randomly associateseach unlock code/identifier pair to an over-lock. In another embodiment,each unlock code/identifier pair is randomly associated with anover-lock using a manual process.

Thus, the present invention enhances the security of the overlocksutilized with the lock management system and reduces risk of comprise ofthe over-locks, as not only are the unlock codes and identifiers arerandomly generated, but these randomly generated values are thenrandomly paired, and randomly associated with respective over-locks.

While the principles of the disclosure have been illustrated in relationto the exemplary embodiments shown herein, the principles of thedisclosure are not limited thereto and include any modification,variation, or permutation thereof.

The invention claimed is:
 1. A method for associating locks with unlockcodes and lock identifiers, the method comprising: selecting a lock tobe marked with a lock identifier and programmed with an unlock code,wherein the lock is not capable of electronic communication, wherein adatabase coupled to a processor stores unlock codes and lockidentifiers, the processor configured to: (i) randomly generate aplurality of unlock codes, (ii) randomly generate a plurality of lockidentifiers, (iii) create a plurality of unlock code/lock identifierpairs by randomly selecting an unlock code from the plurality of unlockcodes, and randomly selecting a lock identifier from the plurality oflock identifiers, and (iv) select an unlock code/lock identifier pairfrom the plurality of unlock code/identifier pairs, wherein the lock ismarked with the selected lock identifier, and wherein the lock isprogrammed with the selected unlock code.
 2. The method of claim 1,wherein the lock identifier is a character string selected from a groupconsisting of numeric characters, alphabet characters, specialcharacters, and alphanumeric characters.
 3. The method of claim 1,wherein the processor utilizes a random number generator to generate theplurality of unlock codes.
 4. The method of claim 1, wherein theprocessor utilizes a random number generator to generate the pluralityof lock identifiers.
 5. The method of claim 1, wherein the processorutilizes a random link generator to create the plurality of unlockcode/lock identifier pairs.
 6. The method of claim 1, wherein theselected unlock code/lock identifier pair is stored in a table in thedatabase.
 7. The method of claim 1, wherein the processor is furtherconfigured to transmit the unlock code is to a mobile device as a textmessage, a multimedia message (MMS), an e-mail, or a secure message. 8.The method of claim 1, wherein the processor is further configured toperform a look-up operation in the database to determine if a customeris associated with the lock.
 9. A method for randomly generating unlockcodes for locks, the method comprising: securing a location with a lock,wherein the lock is not capable of electronic communication, and whereina database coupled to a processor stores an association of the lock anda customer, the processor configured to: (i) randomly generate aplurality of unlock codes, (ii) randomly generate a plurality ofidentifiers, (iii) create an unlock code/identifier pair, wherein theunlock code/identifier pair is created by randomly selecting an unlockcode from the plurality of unlock codes, and randomly selecting anidentifier from the plurality of identifiers, and (iv) associate theunlock code/identifier pair with the lock in the database, wherein theprocessor is further configured to retrieve the unlock code associatedwith the lock from the database and transmit the unlock code to a mobiledevice associated with the customer.
 10. The method of claim 9, whereinthe identifier is a character string selected from a group consisting ofnumeric characters, alphabet characters, special characters, andalphanumeric characters.
 11. The method of claim 9, wherein theprocessor utilizes a random number generator to generate the pluralityof unlock codes.
 12. The method of claim 9, wherein the processorutilizes a random number generator to generate the plurality ofidentifiers.
 13. The method of claim 9, wherein the processor utilizes arandom link generator to create the unlock code/identifier pair.
 14. Themethod of claim 9, wherein the unlock code/identifier pair is associatedwith the lock in a table in the database.
 15. The method of claim 9,wherein the unlock code is transmitted to the mobile device as a textmessage, a multimedia message (MMS), an e-mail, or a secure message. 16.The method of claim 9, wherein the processor is further configured toperform a look-up operation in the database to determine if the customeris associated with the lock.
 17. A system for randomly generating unlockcodes for locks, the system comprising: a lock not capable of electroniccommunication, a database configured to store an association of the lockand customer information, the database further configured to store aplurality of unlock code/identifier pairs, a processor communicativelycoupled to the database, wherein the processor is configured to: (i)randomly generate a plurality of unlock codes, (ii) randomly generate aplurality of identifiers, (iii) create the plurality of unlockcode/identifier pairs, wherein each unlock code/identifier pair iscreated by randomly selecting an unlock code from the plurality ofunlock codes, and randomly selecting an identifier from the plurality ofidentifiers, (iv) select an unlock code/identifier pair from theplurality of unlock code/identifier pairs, and (v) associate theselected unlock code/identifier pair with the lock in the database; amobile device communicatively coupled to the processor, wherein themobile device is configured to transmit customer account information tothe processor; and a transceiver communicatively coupled to theprocessor, wherein the processor is further configured to retrieve theunlock code associated with the lock from the database upon receipt ofthe customer information, and wherein the transceiver is configured totransmit the unlock code to the mobile device.
 18. The system of claim17, wherein the processor is further configured to perform a look-upoperation in the database to determine if the customer informationreceived from the mobile device is associated with the lock.
 19. Thesystem of claim 18, wherein the transceiver if further configured totransmit the unlock code to the mobile device if the customerinformation received from the mobile device is associated with the lock.20. The system of claim 17, wherein the processor is further configuredto randomly associate the unlock code/identifier pair with the lock inthe database.